Location based coreset configuration for transmitting the physical downlink control channel in 5g wireless communication systems

ABSTRACT

The disclosed subject matter relates to techniques for determining an appropriate aggregation level for a control channel resource set (CORESET). In one embodiment, a method is provided that comprises determining, by a first device operatively coupled to a processor, an aggregation level for application by a second device to decode candidate downlink control channels associated with a CORESET. The method further comprises transmitting, by the first device, aggregation level information to the second device indicating the aggregation level. As a result of the transmitting, the second device becomes configured to apply the aggregation level in association with attempting to decode the candidate control downlink control channels. In various embodiments, the aggregation level is determined based one or more criteria, including an aggregation level capability of the second device, a location of the second device relative to the first device, and a geometry associated with the second device.

TECHNICAL FIELD

The disclosed subject matter relates wireless communication systems andmore particularly, to techniques for determining an appropriateaggregation level for transmitting the physical downlink control channel(PDCCH) associated with a control channel resource set (CORESET) in NewRadio (NR) access communication systems.

BACKGROUND

To meet the huge demand for data centric applications, Third GenerationPartnership Project (3GPP) systems and systems that employ one or moreaspects of the specifications of the Fourth Generation (4G) standard forwireless communications are being extended to a Fifth Generation (5G)standard for wireless communications, also referred to as New Radio (NR)access. Compared to existing 4G technologies, 5G is targeting muchhigher throughput with low latency and utilizing higher carrierfrequencies and wider bandwidths, at the same time reducing energyconsumption and costs. 5G networks are also expected to offer systemaccess and services that have different characteristics and connectivitycontrol for future services. In this regard, the NR design needs to behighly flexible and tailored towards new requirements.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example wireless communication systemthat facilitates location-based CORESET configuration for transmittingthe PDCCH in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 2 presents graph illustrating the block error rate (BLER) fordifferent aggregation levels as a function signal-to-noise ratio (SNR)in accordance with various aspects and embodiments of the subjectdisclosure.

FIG. 3 presents a signaling diagram of an example message sequence fortailoring the PDCCH aggregation level for a user equipment (UE) specificCORESET in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 4 presents a signaling diagram of an example message sequence fortailoring the PDCCH aggregation level for a UE specific CORESET inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 5 presents a flow diagram of an example method for tailoring thePDCCH aggregation level for a UE specific CORESET in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 6 presents a high-level flow diagram of an example method fortailoring the PDCCH aggregation level for a UE specific CORESET inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 7 presents a high-level flow diagram of another example method fortailoring the PDCCH aggregation level for a UE specific CORESET inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 8 presents a high-level flow diagram of an example method forreceiving and applying a UE specific aggregation level for decodingcandidate PDCCHs associated with a CORESET in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 9 presents a high-level flow diagram of another example method forreceiving and applying a UE specific aggregation level for decodingcandidate PDCCHs associated with a CORESET in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 10 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 11 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

The following detailed description is merely illustrative and is notintended to limit embodiments and/or application or uses of embodiments.Furthermore, there is no intention to be bound by any expressed orimplied information presented in the preceding sections or in theDetailed Description section.

In many wireless communication systems including 5G NR wirelesscommunication systems, the physical downlink control channel (PDCCH) isused to carry and provide downlink control information (DCI) to the UE,such as information regarding the downlink scheduling assignments andthe uplink scheduling grants. For example, with respect tomultiple-input/multiple-output (MIMO) systems, the DCI typicallyincludes the number of MIMO layers scheduled, transport block sizes,modulation for each codeword, parameters related to hybrid automaticrepeat requests (HARQ), sub-band locations, and the like. However, thespecific contents of the PDCCH can vary based on transmission mode andDCI format.

Legacy long-term evolution (LTE) control channels are distributed acrossthe entire system bandwidth, making it difficult to control intercellinterference. However, NR PDCCHs are specifically designed to transmitin a configurable control channel resource set (CORESET). A CORESET is atime-frequency resource allocation for a UE within which the UE canreceive candidate PDCCHs. A CORESET is analogous to the control regionin LTE but is generalized in the sense that the set of resource blocks(RBs) and the set of orthogonal frequency division multiplex (OFDM)symbols in which it is located are configurable with the correspondingPDCCH search spaces. Such configuration flexibilities of control regionsincluding time, frequency, numerologies, and operating points enable NRto address a wide range of use cases.

For example, the size and location of a CORESET can be configured by thenetwork and thus can be set smaller than the carrier bandwidth. Thefirst CORESET, (referred to as CORESETO) is provided by the masterinformation block (MIB) as part of the configuration of the initialbandwidth part and enables the UE to receive the remaining systeminformation and additional configuration information from the network.After connection setup, the UE can be configured with multiple,potentially overlapping, CORESETs using radio resource control (RRC)signaling protocol. In accordance with existing NR standards, in thetime domain, a CORESET can be up to 3 OFDM symbols in duration andlocated anywhere within the time slot. Existing NR standards furtherdefine a CORESET in the frequency domain using multiples of 6 resourceblocks up to the carrier bandwidth. Frequency allocation in a CORESETconfiguration can be continuous or non-continuous.

A PDCCH is confined to one CORESET and transmitted with its owndemodulation reference signal (DMRS) enabling UE-specific beamforming ofthe control channel. In accordance with existing NR standards, a PDCCHencoded using an aggregation level selected from level a set of fivepossible aggregation levels referred to as level-1, level-2, level-4,level-8 and level-16. These respective aggregation levels correspond todifferent control channel resource elements (CCEs) that can carry thePDCCH, (e.g. level-1 corresponds to 1 CCE, level-2 corresponds to 2CCEs, level-4 corresponds to 4 CCEs and so on). In this regard, the UEneeds to decode each PDCCH using its corresponding aggregation level(e.g., either level-1, level-2, level-4, level-8, or level-16). Thedifferent aggregation levels (or CCE allocations) for the PDCCH are usedto accommodate different DCI payload sizes or different coding rates(also referred to as different DCI formats) for the PDCCH. For example,NR currently defines four different DCI sizes/coding rates (or formats).One size/coding rate is used for the fall back DCI, a second size/codingrate is for scheduling downlink grants, a third size/coding rate is forscheduling uplink grants and a fourth size/coding rate is used for slotformat indication and pre-emption indication depending on theconfiguration.

In accordance with initial NR standards, the UEs are required to blindlymonitor a number of PDCCH candidates of different DCI formats anddifferent aggregation levels. In this regard, for each CORESET assignedto the UE, the UE is required to blindly decode every possible DCIsize/format (e.g., which currently include four) and using everypossible aggregation level (e.g., which currently include five). Thus,the number of each decoding options for each CORESET is twenty, and theUE can be configured with multiple CORESETS (e.g., currently up to fourdifferent CORESETS). Thus, the complexity cost associated with thisblind decoding processing is extensive and not scalable to an increasingnumber of PDCCH sizes/formats and aggregation level combinations.

To limit the UE side complexity in searching/decoding all configuredCORESETs using every different aggregation level, etc., some NRprotocols have been proposed that define NR a confined set of searchspaces for the UE to search and decode. The search space can becharacterizes as set of candidate control channels formed by a CORESETat a given aggregation level which the UE is supposed to attempt todecode. As there are multiple CORESETs, there are multiple searchspaces. Some NR protocols have proposed to restrict the number of searchspaces to ten or lease for each UE. In accordance with restricted searchspace techniques, the network needs to indicate to the UE the definedsearch space and the corresponding aggregation level. With thesetechniques, to further reduce the complexity associated with searchspaces involving many possible aggregation levels, the common practiceis to configure the aggregation level for a given CORESET to a constantvalue. However, using a fixed value for the aggregation level for agiven CORESET is not efficient for 5G systems as it results in usingunnecessary resources for PDCCH, thereby reducing the availableresources for physical downlink shared channel (PDSCH) and consequentlyreducing the link and system throughout.

The disclosed subject matter provides an efficient solution for reducingthe PDCCH search space complexity while optimizing link and systemthrough by tailoring the aggregation level for each UE assigned CORESETbased on UE specific criteria. In various embodiments, the network nodecan determine the appropriate aggregation level for a given UEconfigured CORESET based on one or more criteria including but notlimited to, a known aggregation level capability of the UE, a locationof the UE within the cell (e.g., distance from the UE to the networknode), and/or a geometry of the UE. The network node can further providethe UE with information indicating the determined aggregation level fora given CORESET in the UE specific search space. For example, in variousembodiments, the network node can employ higher layer signaling (e.g.,radio resource control (RRC) signaling and/or media access control (MAC)signaling) to instruct the UE regarding the determined aggregation levelfor a given CORESET configured for the UE. The UE can further beconfigured to apply the aggregation level in association with attemptingto decode the PDCCH candidates corresponding to the given CORESET,thereby reducing the number of blind decoding attempts while optimizingthe amount of PDCCH resources used based on the capability and/orcontext (e.g., needs) of the UE. In this regard, the because disclosedtechniques are efficient in terms of time/frequency resources, theresources required for transmitting the downlink control channel (e.g.,the PDCCH) can be minimized, thereby increasing the amount of availableresources for data transmission. Hence, with increased data transmissionresources, the link and system throughput are improved significantly.

In accordance with one or more embodiments, a first device (e.g., agNodeB or the like) is provided that comprises a processor and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations. These operations cancomprise determining an aggregation level for application by a seconddevice (e.g., a UE) to decode candidate downlink control channelsassociated with a CORESET. The operations further comprise sendingaggregation level information to the second device indicating theaggregation level. Based on the sending, the second device is configuredto apply the aggregation level in association with attempting to decodethe candidate control downlink control channels. In one or moreimplementations, the sending the aggregation level information comprisesemploying a signaling protocol classified as a higher layer signalingprotocol.

In some implementations, the the determining the aggregation levelcomprises selecting the aggregation level from a group of candidateaggregation levels based on a defined criterion. For example, in oneimplementation, the aggregation level can be determined based oncapability information indicating one or more aggregation levelssupported by the second device. In another implementation, theaggregation level can be determined based on a location of the seconddevice. In another implementation, the aggregation level can bedetermined based on a distance between the second device and the firstdevice. For example, with this implementation, the determining theaggregation level can comprise selecting a first aggregation level basedon the distance being less than a defined distance and selecting asecond aggregation level based on the distance being greater than thedefined distance, and wherein the first aggregation level is lower thanthe second aggregation level. In another implementation, the aggregationlevel can be determined based on a geometry associated with the seconddevice. For example, with this implementation, the determining theaggregation level can comprise selecting a first aggregation level basedon the geometry being less than a defined value and selecting a secondaggregation level based on the geometry being greater than the definedvalue, and wherein the first aggregation level is higher than the secondaggregation level.

In various additional embodiments, wherein the determining theaggregation level comprises selecting the aggregation level from a groupof candidate aggregation levels based on a combination of criteriaselected from a group of criteria consisting of: a first criterionapplicable to an aggregation level capability of the second device, asecond criterion applicable to a location of the second device relativeto the first device, and a third criterion applicable to a geometryassociated with the second device.

In accordance with one or more embodiments, a first device (e.g., a UEor the like) is provided that comprises a processor and a memory thatstores executable instructions that, when executed by the processor,facilitate performance of operations. These operations can comprisereceiving aggregation level information from a second device (e.g., agNodeB) indicating an aggregation level for a CORESET, wherein theaggregation level was selected by the second device from candidateaggregation levels based on a defined criterion. The operations furthercomprise, based on the receiving, employing the aggregation level inassociation with attempting to decode candidate downlink controlchannels associated with the CORESET. For example, the defined criterioncan be evaluated with respect to a group of device criteria consistingof: an aggregation level capability of the first device, a location ofthe first device relative to the second device, and a geometryassociated with the first device. In some implementations, theaggregation level information comprises first aggregation levelinformation, the aggregation level comprises a first aggregation level,and wherein the operations further comprise receiving second aggregationlevel information from the second device indicating a second aggregationlevel for the CORESET, wherein the second aggregation level was selectedby the second device from the candidate aggregation levels based on achange to the defined criterion. The operations further comprise basedon the receiving, employing the second aggregation level instead of thefirst aggregation level in association with the attempting to decode thecandidate downlink control channels.

In some embodiments, elements described in connection with the disclosedsystems can be embodied in different forms such as acomputer-implemented method, a computer-readable or machine-readablestorage medium, or another form.

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. The following description and the annexed drawings set forthin detail certain illustrative aspects of the subject matter. However,these aspects are indicative of but a few of the various ways in whichthe principles of the subject matter can be employed. Other aspects,advantages, and novel features of the disclosed subject matter willbecome apparent from the following detailed description when consideredin conjunction with the provided drawings. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the subject disclosure. Itmay be evident, however, that the subject disclosure may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the subject disclosure. The terms scheme,protocol, configuration and the like, are used interchangeablythroughout the specification in various contexts to refer to a definedmanner for formatting, transmitting or receiving information.

FIG. 1 is an illustration of an example wireless communication system100 that facilitates location-based CORESET configuration fortransmitting the PDCCH in accordance with various aspects andembodiments of the subject disclosure. System 100 can comprise aplurality of UEs 102 and a radio network node 104. The non-limiting termuser equipment (UE) is used herein to refer to any type of wirelessdevice that can communicate with a radio network node in a cellular ormobile communication system. Some examples UEs can include but are notlimited to, a target device, a device to device (D2D) UE, a machine typeUE or UE capable of machine to machine (M2M) communication, a portabledigital assistant (PDA), a tablet personal computer (PC), a mobileterminal, a smart phone, a laptop, a laptop embedded equipped (LEE), alaptop mounted equipment (LME), USB dongles, a wearable device, avirtual reality (VR) device, a heads-up display (HUD) device, a smartcar, and the like. In one or more embodiments, the respective UEs 102(and network node 104) can include two or more antennas (not shown)thereby supporting multiple-input and multiple output (MIMO)communications in association 5G NR communication schemes with phasetracking. The number of antennas provided on a UE 102 can vary (e.g.,from two to hundreds or more to accommodate massive MIMO systems). Inthis regard, in accordance with various embodiments, wirelesscommunication system 100 can be or include a MIMO system. MIMO systemscan significantly increase the data carrying capacity of wirelesssystems. For these reasons, MIMO is an integral part of the 3GPP and4GPP generation wireless systems. Wireless communication system 100 canfurther support the massive MIMO communication protocols introduced by5G NR that employ hundreds of antennas at the transmitter side andreceiver side.

In this regard, various embodiments are applicable to single carrier aswell as to multicarrier (MC) or carrier aggregation (CA) operation ofthe UE in conjunction with MIMO in which the UE is able to receiveand/or transmit data to more than one serving cells using MIMO. However,the various techniques described herein are not limited to use in MIMOsystems and can be applied to other wireless communication systems(e.g., uplink and side link systems). The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. It is noted that the solutions outlinedequally applies for Multi RAB (radio bearers) on some carriers (that isdata plus speech is simultaneously scheduled). Similarly, the solutionsare applicable where some UEs 102 are scheduled using eMBB, some UEs 102are scheduled using URLLC, and some UEs 102 are using mMTC applications.

In the embodiment shown, system 100 is or includes a wirelesscommunication network serviced by one or more wireless communicationnetwork providers. The UEs 102 can be communicatively coupled to thewireless communication network via the network node 104. In this regard,a UE 102 can send and/or receive communication data via a wireless linkor channels to the network node 104. For example, the dashed arrow linesfrom the network node 104 to example UE1 represent downlinkcommunications and the solid arrow lines represent uplinkcommunications. It should be appreciated that these arrow lines aremerely provided to demonstrate wireless communication links between a UEand the network node 104. In this regard, although arrowed lines are notdrawn for every depicted UE 102, it should be appreciated that alldepicted UEs can wirelessly communicate with the network node 104 usinguplink and downlink communications.

The non-limiting term network node (or radio network node) is usedherein to refer to any type of network node serving a UE 102 and/orconnected to another network node, network element, or another networknode from which the UE 102 can receive a radio signal. Examples ofnetwork nodes (e.g., network node 104) can include but are not limitedto: a base station (BS) device, a Node B device, a multi-standard radio(MSR) device (e.g., an MSR BS), a gNodeB device, an eNode B device, anetwork controller device, a radio network controller (RNC) device, abase station controller (BSC) device, a relay device, a donor nodedevice controlling relay, a base transceiver station (BTS) device, anaccess point (AP) device, a transmission point device, a transmissionnode, an RRU device, an RRH device, node devices in distributed antennasystem (DAS), and the like. In accordance one or more embodiment, thenetwork node 104 can include two or more antennas to support variousMIMO and/or massive MIMO communications in association phase tracking.

System 100 can further include one or more communication serviceprovider networks 106 that facilitate providing wireless communicationservices to various UEs, including UE 102, via the network node 104and/or various additional network devices (not shown) included in theone or more communication service provider networks 106. In theembodiment shown, the area defined by the hexagon indicates a singlewireless network cell 110 serviced by the network node 104. It should beappreciated however that system 100 can include a plurality of cellsrespectively serviced by network nodes that are respectivelycommunicatively coupled to the one or more communication serviceprovider networks 106. In this regard, the one or more communicationservice provider networks 106 can include various types of disparatenetworks, including but not limited to: cellular networks, femtonetworks, picocell networks, microcell networks, internet protocol (IP)networks Wi-Fi service networks, broadband service network, enterprisenetworks, cloud-based networks, and the like. For example, in at leastone implementation, system 100 can be or include a large-scale wirelesscommunication network that spans various geographic areas. According tothis implementation, the one or more communication service providernetworks 106 can be or include the wireless communication network and/orvarious additional devices and components of the wireless communicationnetwork (e.g., additional network devices and cell, additional UEs,network server devices, etc.). The network node 104 can be connected tothe one or more communication service provider networks 106 via one ormore backhaul links 108. For example, the one or more backhaul links 108can include wired link components, such as but not limited to: like aT1/E1 phone line, a digital subscriber line (DSL) (e.g., eithersynchronous or asynchronous), an asymmetric DSL (ADSL), an optical fiberbackbone, a coaxial cable, and the like. The one or more backhaul links108 can also include wireless link components, such as but not limitedto, line-of-sight (LOS) or non-LOS links which can include terrestrialair-interfaces or deep space links (e.g., satellite communication linksfor navigation.

Although the subject disclosure is directed to systems employing 5G orNR communications technologies, it should be appreciated that system 100can employ various wireless communication technologies to facilitatewireless radio communications between devices (e.g., the UE 102 and thenetwork node 104). In this regard, the disclosed techniques for CSIestimation in association with PTRS integration can be applied to anyRAT or multi-RAT system where the UE operates using multiple carriers,such as but not limited to: long term evolution (LTE), frequencydivision duplex (FDD), time division duplex (TDD), FDD/TDD, widebandcode division multiple access (WCMDA), high speed packet access (HSPA),WCMDA/HSPA, global system for mobile communication (GSM), 3GGP,GSM/3GGP, Wi Fi, WLAN, WiMax, CDMA2000, and the like.

As discussed above, in NR communication systems such as system 100, thenetwork node 104 communicates DCI to the UE 102 using one of severalpossible configurable PDCCHs. For example, each CORESET can hold severaldifferent PDDCHs of various DCI sizes/formats and a UE 102 can beconfigured with a plurality of CORESETs (e.g., one to four according tocurrent 5G specifications). In addition, each candidate PDCCH can beencoded using one of several possible aggregation levels (e.g., level-1,level-2, level-4, level-8 and level-16). In order to restrict the UE 102from searching through all CORSESTs configured for UE for the manycandidate PDCCHs and attempting to decode each candidate PDCCH usingevery possible aggregation level (e.g., 1, 2, 4, 6, 8 or 18), NRprotocols have defined restricted search spaces for the UE. A singlesearch space indicates the possible candidate PDCCHs which the UE shouldattempt to decode within the one or more CORESETs assigned to the UE 102and using a single aggregation level. In order to further reduce thecomplexity associated with the number of candidate PDCCHs andcorresponding UE decoding attempts, NR protocols have resorted toconfiguring the aggregation level for a given CORESET to a constantvalue. This means that that the network node 104 would apply the sameaggregation level for each PDCCH of each CORESET for all the UEs 102 inthe cell 110, significantly overutilizing unnecessary resources in manyscenarios, such as scenarios in which lower aggregation levels could beused without scarifying performance quality.

System 100 provides a much more efficient solution for reducing thePDCCH search space complexity while optimizing link and system throughby tailoring the aggregation level for each UE assigned CORESET based onUE 102 specific criteria. In particular, instead of applying the sameaggregation level for respective CORESETs used by all UEs 102 in thecell 110, in accordance with the disclosed techniques, the network node104 can tailor the aggregation level for a given CORESET assigned to theUE 102 (e.g., by the network node 104) based on one or more UE specificcriteria. For example, in some embodiments, the network node 104 canselect an appropriate aggregation level for encoding the PDCCH from adefined set of possible aggregation levels based on one or more UEspecific criteria. For instance, the defined set of aggregation levelscan include NR aggregation level-1, level-2, level-4, level-8 andlevel-16. In other embodiments, the network node 104 can determine anew, UE specific aggregation level (e.g., an aggregation level betweenor beyond aggregation level-1, level-2, level-4, level-8 and level-16)for encoding the PDCCH for a given UE 102 and assigned CORESET based onthe one or more UE specific criteria.

The UE specific criteria can include predefined performance criteria. Invarious embodiments, the UE specific criteria can include one, or acombination of two or more, of the following: a known aggregation levelcapability of the UE 102, a location of the UE 102 within the cell(e.g., a distance from the UE 102 to the network node 104), and/or ageometry of the UE. For example, in various implementations, a UE 102may not be capable of supporting all possible aggregation levels.

For instance, a UE may support only one or a subset of the possibleaggregation levels (e.g., one or a subset of aggregation levels includedin a group comprising level-1, level-2, level-4, level-8 and level 16).For example, some UEs 102 may support only lower level aggregationlevels 1, 2 and 4, while other may support only higher aggregationlevels 8 and 16. Thus, in one or more embodiments, the network node 104can receive UE aggregation level capability information from a UE 102indicating the one or more aggregation levels supported by the UE. Forexample, the UE 102 can be configured to provide the UE aggregationlevel capability information at the time of initial link set-up,registration of the UE with the network provider, or in another suitablemanner. In other implementations, the network node 104 can look up UEaggregation level capability in a network accessible database based onknown information about the UE (e.g., a type of the UE, a uniqueidentifier for the UE, or the like). Regardless of the manner in whichthe network node 104 obtains aggregation level capability informationfor a UE 102, the network node 104 can employ the UE aggregation levelcapability information to restrict the possible aggregation levels forusing for the PDCCH based on those which the UE is capable ofsupporting. In some implementations in which the UE capability isunknown or cannot be determined, the network node 104 can apply adefault aggregation level capability restriction. For example, thedefault aggregation level capability restriction can include apredefined subset (e.g., one or more) of the possible aggregationlevels. For instance, if the UE capability is unknown or cannot bedetermined, the network node 104 can assume the UE is capable ofsupporting a default aggregation level (e.g., level-8) or a subset ofdefault aggregation levels (e.g., level-4 and level-8).

Selection of the aggregation level based on UE location is rooted in theobserved correlation between UE location within the cell,signal-to-noise ratio (SNR) and block error rate (BLER) at differentaggregation levels. In particular, SNR generally increases as the UE 102moves closer to the network node 104 and decreases as the UE moves awayfrom the network node. For example, lower SNR is more frequentlyobserved at the cell 110 edge while higher SNR is more frequentlyobserved at the cell 110 centre.

FIG. 2 presents graph 200 illustrating the block error rate (BLER) fordifferent aggregation levels as a function signal-to-noise ratio (SNR)in accordance with various aspects and embodiments of the subjectdisclosure. As shown in graph 200, the BLER performance depends on theaggregation level and the specific SNR. In this regard, for allaggregation levels, the BLER decreases as the SNR increases. However,the lower aggregation levels (e.g., AL-2 and AL-4) provide sufficientlylow BLER (e.g., good performance) at higher SNR levels. Thus, lowaggregation levels (e.g., AL-1, AL-2, and AL-4), can provide good BLERperformance in scenarios when the SNR is high. On the other hand, whenSNR is low higher aggregation levels (e.g., AL-8 and AL-16) can be usedto achieve good BLER performance.

Thus, in various embodiments, the network node 104 can be configured todetermine/select the appropriate aggregation level based on the distancebetween the UE 102 and the network node, wherein the closer the UE 102to the network node 104 lower the SNR and thus the lower the aggregationlevel. For example, when the UE 102 is nearer to the network node 104,the network node 104 can configure the UE to use a lower aggregationlevel (e.g., AL-1, AL-2 or AL-4). This is because at the cell centre theUE generally have a high SNR. Similarly, when the UE 102 is at the celledge, the network node 104 can configure the UE to use a higheraggregation level (e.g., AL-8 or AL-16). In various embodiments thenetwork node 104 can employ predefined distance ranges or thresholds fordetermining the appropriate aggregation level. For example, at adistance less than “n” meters between the UE 102 and the network node,the network node can apply a first aggregation level (e.g., AL-1), at adistance greater than “n” meters and less than “m” meters the networknode can apply a second aggregation level higher than the firstaggregation level (e.g., AL-2), at a distance greater than “m” metersand less than “p” meters the network node can apply a third aggregationlevel higher than the second aggregation level (e.g., AL-4), and so on.

In other embodiments in which the network node 104 receives and/ordetermines information regarding the SNR experience bey the UE, thenetwork node 104 can determine the aggregation level based on the SNR,wherein lower aggregation levels are used for high SNRs and higheraggregation levels are used for low SNR. For example, with theseembodiments, the network node 104 can apply similar SNR thresholdsand/or ranges assigned to different aggregation levels. For example, thenetwork node 104 can employ defined aggregation level to SNR levelcriteria such as: SNRs less than “x” can be assigned a first aggregationlevel (e.g., AL-16); SNRs greater than “x” can be assigned a secondaggregation level less than the first aggregation level (e.g., AL-8),and so on.

The UE geometry criterion can also be employed by the network node 104(in addition to and/or alternative to the location criterion) todetermine an appropriate aggregation level to direct the UE to apply inassociation with decoding candidate PDCCHs for a given CORESET. Thegeometry of the UE can be determined as a function of thesignal-to-interference plus noise ratio (SINR) and/or the CQI reportedby the UE 102. For example, in some implementations, the UE geometry canbe determined by the network node (and/or the UE and reported by theUE), by averaging the SINR for example uplink channel estimates. Inother implementations, the UE geometry can be determined by averagingthe CQI reported by the UE. With respect to UE geometry, the networknode 104 can assign higher aggregation levels to lower UE geometries(e.g., lower SINR) and lower aggregation levels to higher UE geometries(e.g., higher SNR). For example, the network node 104 can employ definedaggregation level to UE geometry criteria such as: geometries less than“y” can be assigned a first aggregation level (e.g., AL-8); geometriesgreater than “y” can be assigned a second aggregation level lower thanthe first aggregation level (e.g., AL-4), and so on.

In some embodiments, the network node 104 can employ one of the abovenoted criterion to determine the appropriate aggregation level forapplication by the UE in association with decoding candidate PDCCHs fora given CORESET. In other embodiments, the network node can employ acombination of two or more of the above noted criterion. In someembodiments in which the UE is configured with more than one CORESET,the network node 104 can determine or select a single aggregation levelfor all of the CORESETs. In other embodiments, the network node 104 candetermine or select a different aggregation level for two or more of theCORESETs. In this regard, the network node 104 can tailor theaggregation level for each CORESET based on the UE specific criteria. Asa result, in some implementation, two or more CORESETS assigned to theUE can receive different aggregation level assignments.

The network node 104 can further encode the PDCCH with the determined orselected aggregation level for the CORESET in which the PDCCH isprovided. In addition, the network node 104 can instruct the UE 102 toapply only the determined or selected aggregation level in associationwith decoding the candidate PDCCHs for the corresponding CORESET. Inthis regard, the network node 104 can inform the UE regarding theselected/determined aggregation level for a given CORESET. Based onreception of information identifying the selected/determined aggregationlevel for a given CORESET, the UE 102 can further be configured to applythe selected/determined aggregation level in association with attemptingto decode the candidate PDCCHs corresponding to the given CORESET. Invarious embodiments, the network node 104 can employ higher layersignalling (e.g., radio resource control (RRC) signalling and/or mediaaccess control (MAC) signalling) to instruct the UE regarding thedetermined aggregation level for a given CORESET configured for the UE.

With the disclosed techniques for selecting/determining the PDCCHaggregation level by the network node 104 for a CORESETassigned/configured for a UE 102 based on a known capability, location,and/or geometry of the UE 102, and instructing the UE 102 to apply onlythe selected/determined aggregation level to decode the candidate PDCCHsassociated with that CORESET, the number of blind decoding attemptsrequired by the UE is significantly reduced. In addition, the time andfrequency resources used for the PDCCHs for the collective UEs in thecell 110 are efficiently distributed base on UE capability and/or (e.g.,needs) of the UE. As a result, the amount of available resources fordata transmission are increased, thereby enhancing link and systemthroughput.

FIG. 3 presents a signaling diagram of an example message sequence 300for tailoring the PDCCH aggregation level for a UE specific CORESET inaccordance with various aspects and embodiments of the subjectdisclosure. Message sequence 300 particularly exemplifies a process fordownlink data transfer in 5G/NR systems. Message sequence 300 involvesdetermining an aggregation level for a UE (e.g., UE 102) by the networknode (e.g., network node 104), and communicating the aggregation levelto the UE. Message sequence 300 also exemplifies the UE side responsebased on reception of the aggregation level. Repetitive description oflike elements employed in respective embodiments is omitted for sake ofbrevity.

At 302, the network node 104 can send cell specific/UE specificreference signals in accordance with standard downlink data transferinitiation. From the pilot or reference signals, the UE computes thechannel estimates and the computes the parameters needed for channelstate information (CSI) reporting. The UE 102 can further send the CSIreport to the network node 104 via an uplink feedback channel, either onrequest from the network or periodically. The network scheduler uses theCSI information in choosing the parameters for scheduling of the UE. Thenetwork node 104 sends the scheduling parameters to the UE as DCI in thedownlink control channel (e.g., the PDCCH). After that the actual datatransfer can take place from the network node 104 to the UE.

In accordance with 5G/NR signalling, the DCI can be encoded in one of aplurality of possible PDCCHs respectively associated with one or moreCORESETs assigned to the UE 102. In this regard, the CORESET is definedfrom the UE perspective and only indicates where (e.g., search spaces)the UE 102 may receive PDCCH transmissions. The CORESET configurationinformation assigned to the UE by the network node 104 does not providethe UE with confirmation that the network node 104 will be or hastransmitted a PDCCH to the UE. In addition, at no point does the networknode 104 provide the UE 102 with information indicating where/how thePDCCH while be specifically configured if and when it is sent (e.g., thespecific CORESET where it will be if more than one CORESET is assignedto the UE, the specific DCI size/format, the specific time/frequencyresources that will be used, the specific numerology that will be used,etc.).

However, with the disclosed signalling techniques, at 304, the networknode 104 can determine an aggregation level (for encoding/decoding thePDCCH) for each CORESET assigned to the UE based on UE specificaggregation level criteria. For example, the network node 104 candetermine or select the most appropriate aggregation level (e.g., AL-1,AL-2, AL-4, AL-8 or AL-16) for encoding/decoding the PDCCH based on oneor more of: a known aggregation level supported by the UE, a location ofthe UE relative to the network node 104, a SNR reported by the UE inassociation with reception of signals (e.g., reference signals) from thenetwork node 104, and a geometry of the UE. For example, in someimplementations, if the UE is configured with a plurality of CORESETs,the network node 104 can determine different aggregation levels for theUE to use for two or more of the different CORESETs. In otherimplementations, if the UE is configured with a plurality of CORESETs,the network node 104 can determine a single aggregation level for the UEto apply to all of the CORESETs.

At 306, the network node 104 can send the UE CORESET specificaggregation level information indicating the selected/determinedaggregation level for each CORESET. In various embodiments, the networknode 104 can send the aggregation level information to the UE usinghigher layer signalling (e.g., an RRC signalling protocol and/or a MACsignalling protocol). At 308, the UE can send the network node 104 withfeedback (e.g., CSI feedback) via an uplink feedback channel. At 310,the network node may send the UE with possible DCI via a PDCCH fromamong a plurality of candidate downlink control channels. At 312, the UEcan employ the CORESET specific aggregation level to attempt to decodethe associated candidate downlink control channels. If the UE receivesand successfully decodes the PDCCH, at 314, the UE can then receive datavia the data traffic channel.

FIG. 4 presents a signaling diagram of another example message sequence400 for tailoring the PDCCH aggregation level for a UE specific CORESETin accordance with various aspects and embodiments of the subjectdisclosure. Message sequence 400 also exemplifies a process for downlinkdata transfer in 5G/NR systems. Message sequence 400 involvesdetermining an aggregation level for a UE (e.g., UE 102) by the networknode (e.g., network node 104), and communicating the aggregation levelto the UE. Message sequence 400 also exemplifies the UE side responsebased on reception of the aggregation level. Message sequence 400 issimilar or substantially similar with addition of a few notablevariations. Repetitive description of like elements employed inrespective embodiments is omitted for sake of brevity.

Similar to messaging sequence 400, at 402, the network node 104 can sendcell specific/UE specific reference signals in accordance with standarddownlink data transfer initiation. At 404, the network node 104 candetermine an aggregation level (for encoding/decoding the PDCCH) for theCORESET (or CORESETs) assigned to the UE. In some implementations, at404, the network node 104 can determine the initial aggregation levelbased on UE specific aggregation level criteria. For example, thenetwork node 104 can determine or select the most appropriateaggregation level (e.g., AL-1, AL-2, AL-4, AL-8 or AL-16) forencoding/decoding the PDCCH based on one or more of: a known aggregationlevel supported by the UE, a location of the UE relative to the networknode 104, a SNR reported by the UE in association with reception ofsignals (e.g., reference signals) from the network node 104, and ageometry of the UE. In other implementations, at 404 the network nodecan apply a default aggregation level (e.g., a pre-set aggregation levelnot specific to the UE) for application by the UE to decode allcandidate PDCCHs. In either of these implementations, if the UE isconfigured with a plurality of CORESETs, the network node 104 candetermine a single or different aggregation levels for the UE to use fortwo or more of the different CORESETs.

At 406, the network node 104 can send the UE CORESET specificaggregation level information indicating the selected/determinedaggregation level for each CORESET. In various embodiments, the networknode 104 can send the aggregation level information to the UE 102 usinghigher layer signalling (e.g., an RRC signalling protocol and/or a MACsignalling protocol). At 408, the UE can send the network node 104 withfeedback (e.g., CSI feedback) via an uplink feedback channel. At 410,the network node may send the UE with possible DCI via a PDCCH fromamong a plurality of candidate downlink control channels. At 412, the UE102 can employ the CORESET specific aggregation level to attempt todecode the associated candidate downlink control channels. If the UEreceives and successfully decodes the PDCCH, at 414, the UE can thenreceive data via the data traffic channel.

At 416, the network node 104 can review the UE specific aggregationlevel criteria and update the initial aggregation level for the CORESET(or CORESETs) assigned to the UE if appropriate. For example, thenetwork node 104 can be configured to periodically check the selectioncriteria for the aggregation level and determine if based on theselection criteria that, the initial configured aggregation level shouldbe changed. In this regard, at 416, the network node 104 can determineif the initial aggregation level is appropriate based on a knownaggregation level supported by the UE, a location of the UE relative tothe network node 104, a SNR reported by the UE in association withreception of signals (e.g., reference signals) from the network node104, and a geometry of the UE. For example, if the selection criterionwas not initially reviewed at 404 (e.g., a default aggregation level wasapplied), the network node 104 can now apply the selection criteria at416 to determine whether the initial aggregation level satisfies theselection criteria. In another implementation, if the selectioncriterion was applied at 404, but the UE location has now changed, thereported SNR has changed and/or the UE geometry has changed, the initialaggregation level may no longer be the most appropriate aggregationlevel. Accordingly, at 416, the network node 104 can determine if theinitial aggregation level is appropriate for the current UE specificperformance parameters (e.g., if the initial aggregation level isappropriate based on the current UE location/geometry). If the networknode determines a different aggregation level is more appropriate basedon the current UE specific performance parameters, then the network node104 can determine an updated aggregation level based on the current UEspecific performance parameters. Then at 418 the network node 404 cansend the UE 102 the updated CORESET specific aggregation levelinformation (e.g., using higher layer signalling), and the UE 102 canbegin to use the updated aggregation level instead of the initialaggregation level to decode the candidate PDCCHs.

FIG. 5 presents a flow diagram of an example method 500 for tailoringthe PDCCH aggregation level for a UE specific CORESET in accordance withvarious aspects and embodiments of the subject disclosure. Repetitivedescription of like elements employed in respective embodiments isomitted for sake of brevity.

At 502, the network node 104 can select an aggregation level for theCORESET (or CORESETs) assigned to the UE based on UE specificaggregation level criteria (e.g., capability, location, geometry, etc.).At 504, the network node 104 can send aggregation level information tothe UE indicating the selected aggregation level. At 506, the networknode can determine if the connection/link between the UE and the networknode is maintained. If not, then method 500 can end. However, if theconnection is maintained, at 510 the network node can periodicallyrecheck the UE specific aggregation level criteria. At 512, the networknode can determine if the current UE location and/or geometry indicatesa new aggregation level is more appropriate than the last aggregationlevel. If not, then method 500 can proceed back to 506 can continueaccordingly. However, if at 512 the network node determines that thecurrent UE location and/or geometry indicates a new aggregation level ismore appropriate than the last aggregation level, then at 514 thenetwork node can select the new aggregation level for use by the UE inassociation with decoding the PDCCH. At 516, the network node can sendupdated aggregation level information to the UE indicating the newaggregation level. Method 500 can further continue from 506 until theconnection is no longer maintained.

FIG. 6 presents a high-level flow diagram of an example method 600 fortailoring the PDCCH aggregation level for a UE specific CORESET inaccordance with various aspects and embodiments of the subjectdisclosure. Method 600 provides an exemplary method for performance by anetwork node (e.g., network node 104) of a wireless communicationnetwork 100 in association serving a UE of the wireless communicationnetwork. Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity.

At 602, a first device operatively coupled to a processor (e.g., networknode 104), determines an aggregation level for application by a seconddevice (e.g., UE 102) to decode candidate downlink control channelsassociated with a CORESET. At 604, the first device transmitsaggregation level information to the second device indicating theaggregation level. In various embodiments, based on the transmitting,the second device employs the aggregation level in association withattempting to decode the candidate downlink control channels.

FIG. 7 presents a high-level flow diagram of another example method 700for tailoring the PDCCH aggregation level for a UE specific CORESET inaccordance with various aspects and embodiments of the subjectdisclosure. Method 700 also provides an exemplary method for performanceby a network node (e.g., network node 104) of a wireless communicationnetwork 100 in association serving a UE of the wireless communicationnetwork. Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity.

At 702, a first device operatively coupled to a processor (e.g., networknode 104), determines an aggregation level for application by a seconddevice (e.g., UE 102) to decode candidate downlink control channelsassociated with a CORESET. At 704, the first device sends aggregationlevel information to the second device indicating the aggregation level.In various embodiments, based on the sending, the second device employsthe aggregation level in association with attempting to decode thecandidate downlink control channels. At 706, the first device determinesan updated aggregation level for application by the second device todecode the candidate downlink control channels based on a change inallocation or geometry of the second device. At 708, the first devicesends updated aggregation level information to the second deviceindicating the updated aggregation level. In various embodiments, basedon the sending the second device employs the updated aggregation levelinstead of the aggregation level in association with the attempting todecode the candidate downlink control channels.

FIG. 8 presents a high-level flow diagram of an example method 800 forreceiving and applying a UE specific aggregation level for decodingcandidate PDCCHs associated with a CORESET in accordance with variousaspects and embodiments of the subject disclosure. Method 800 providesan exemplary method for performance by a UE (e.g., UE 102) of a wirelesscommunication network 100 in association communication with a networknode (e.g., network node 104) servicing a cell in which the UE islocated. Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity.

At 802, a first device operatively coupled to a processor (e.g., UE102), receives aggregation level information from a second device (e.g.,network node 104) indicating an aggregation level for a CORESET, whereinthe aggregation level was selected by the second device from candidateaggregation levels based on a defined criterion. At 804, based on thereceiving, the first device employs the aggregation level in associationwith attempting to decode candidate downlink control channels associatedwith the CORESET.

FIG. 9 presents a high-level flow diagram of another example method forreceiving and applying a UE specific aggregation level for decodingcandidate PDCCHs associated with a CORESET in accordance with variousaspects and embodiments of the subject disclosure. Method 900 alsoprovides an exemplary method for performance by a UE (e.g., UE 102) of awireless communication network 100 in association communication with anetwork node (e.g., network node 104) servicing a cell in which the UEis located. Repetitive description of like elements employed inrespective embodiments is omitted for sake of brevity.

At 902, a first device operatively coupled to a processor (e.g., UE102), receives first aggregation level information from a second device(e.g., network node 104) indicating a first aggregation level for aCORESET, wherein the aggregation level was selected by the second devicefrom candidate aggregation levels based on a defined criterion specificto the first device. At 904, based on the receiving, the first deviceemploys the first aggregation level in association with attempting todecode candidate downlink control channels associated with the CORESET.At 906, the first device receives second aggregation level informationfrom the second device indicating a second aggregation level for theCORESET, wherein the second aggregation level was selected by the seconddevice from the candidate aggregation levels based on a change to thedefined criterion. At 908, based on the receiving, the first deviceemploys second aggregation level instead of the first aggregation levelin association with the attempting to decode the candidate downlinkcontrol channels.

FIG. 10 is a schematic block diagram of a computing environment 1000with which the disclosed subject matter can interact. The system 1000comprises one or more remote component(s) 1010. The remote component(s)1010 can be hardware and/or software (e.g., threads, processes,computing devices). In some embodiments, remote component(s) 1010 cancomprise servers, personal servers, wireless telecommunication networkdevices, RAN device(s), etc. As an example, remote component(s) 1010 canbe network node 104, one or more devices included in the communicationservice provider networks 106, and the like. The system 1000 alsocomprises one or more local component(s) 1020. The local component(s)1020 can be hardware and/or software (e.g., threads, processes,computing devices). In some embodiments, local component(s) 1020 cancomprise, for example, a UE 102, one or more components of the UE 102,and the like etc.

One possible communication between a remote component(s) 1010 and alocal component(s) 1020 can be in the form of a data packet adapted tobe transmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 1010 and a localcomponent(s) 1020 can be in the form of circuit-switched data adapted tobe transmitted between two or more computer processes in radio timeslots. The system 1000 comprises a communication framework 1040 that canbe employed to facilitate communications between the remote component(s)1010 and the local component(s) 1020, and can comprise an air interface,e.g., Uu interface of a UMTS network, via an LTE network, etc. Remotecomponent(s) 1010 can be operably connected to one or more remote datastore(s) 1050, such as a hard drive, solid state drive, SIM card, devicememory, etc., that can be employed to store information on the remotecomponent(s) 1010 side of communication framework 1040. Similarly, localcomponent(s) 1020 can be operably connected to one or more local datastore(s) 1030, that can be employed to store information on the localcomponent(s) 1020 side of communication framework 1040.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 11, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules comprise routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can comprise both volatile and nonvolatilememory, by way of illustration, and not limitation, volatile memory 1120(see below), non-volatile memory 1122 (see below), disk storage 1124(see below), and memory storage 1146 (see below). Further, nonvolatilememory can be included in read only memory, programmable read onlymemory, electrically programmable read only memory, electricallyerasable read only memory, or flash memory. Volatile memory can compriserandom access memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as synchronous random access memory, dynamic randomaccess memory, synchronous dynamic random access memory, double datarate synchronous dynamic random access memory, enhanced synchronousdynamic random access memory, Synchlink dynamic random access memory,and direct Rambus random access memory. Additionally, the disclosedmemory components of systems or methods herein are intended to comprise,without being limited to comprising, these and any other suitable typesof memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, comprising single-processoror multiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,notebook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 11 illustrates a block diagram of a computing system 1100 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1112, which can be, for example, a UE (e.g., UE102), a network node (e.g., network node 104), or the like, can comprisea processing unit 1114, a system memory 1116, and a system bus 1118.System bus 1118 couples system components comprising, but not limitedto, system memory 1116 to processing unit 1114. Processing unit 1114 canbe any of various available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1114.

System bus 1118 can be any of several types of bus structure(s)comprising a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures comprising, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 11164), and small computer systems interface.

System memory 1116 can comprise volatile memory 1120 and nonvolatilememory 1122. A basic input/output system, containing routines totransfer information between elements within computer 1112, such asduring start-up, can be stored in nonvolatile memory 1122. By way ofillustration, and not limitation, nonvolatile memory 1122 can compriseread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1120 comprises read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1112 can also comprise removable/non-removable,volatile/non-volatile computer storage media. FIG. 11 illustrates, forexample, disk storage 1124. Disk storage 1124 comprises, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1124 can comprise storage media separately or in combination with otherstorage media comprising, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1124to system bus 1118, a removable or non-removable interface is typicallyused, such as interface 1126.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, read only memory, programmable readonly memory, electrically programmable read only memory, electricallyerasable read only memory, flash memory or other memory technology,compact disk read only memory, digital versatile disk or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can comprisenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,cause a system comprising a processor to perform operations, comprisinggenerating an RRC connection release message further comprisingalterative band channel data.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media.

It can be noted that FIG. 11 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1100. Such software comprises an operating system1128. Operating system 1128, which can be stored on disk storage 1124,acts to control and allocate resources of computer system 1112. Systemapplications 1130 take advantage of the management of resources byoperating system 1128 through program modules 1132 and program data 1134stored either in system memory 1116 or on disk storage 1124. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1112 throughinput device(s) 1136. In some embodiments, a user interface can allowentry of user preference information, etc., and can be embodied in atouch sensitive display panel, a mouse/pointer input to a graphical userinterface (GUI), a command line controlled interface, etc., allowing auser to interact with computer 1112. Input devices 1136 comprise, butare not limited to, a pointing device such as a mouse, trackball,stylus, touch pad, keyboard, microphone, joystick, game pad, satellitedish, scanner, TV tuner card, digital camera, digital video camera, webcamera, cell phone, smartphone, tablet computer, etc. These and otherinput devices connect to processing unit 1114 through system bus 1118 byway of interface port(s) 1138. Interface port(s) 1138 comprise, forexample, a serial port, a parallel port, a game port, a universal serialbus, an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1140 use someof the same type of ports as input device(s) 1136.

Thus, for example, a universal serial busport can be used to provideinput to computer 1112 and to output information from computer 1112 toan output device 1140. Output adapter 1142 is provided to illustratethat there are some output devices 1140 like monitors, speakers, andprinters, among other output devices 1140, which use special adapters.Output adapters 1142 comprise, by way of illustration and notlimitation, video and sound cards that provide means of connectionbetween output device 1140 and system bus 1118. It should be noted thatother devices and/or systems of devices provide both input and outputcapabilities such as remote computer(s) 1144.

Computer 1112 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1144. Remote computer(s) 1144 can be a personal computer, a server, arouter, a network PC, cloud storage, a cloud service, code executing ina cloud-computing environment, a workstation, a microprocessor basedappliance, a peer device, or other common network node and the like, andtypically comprises many or all of the elements described relative tocomputer 1112. A cloud computing environment, the cloud, or othersimilar terms can refer to computing that can share processing resourcesand data to one or more computer and/or other device(s) on an as neededbasis to enable access to a shared pool of configurable computingresources that can be provisioned and released readily. Cloud computingand storage solutions can storing and/or processing data in third-partydata centers which can leverage an economy of scale and can viewaccessing computing resources via a cloud service in a manner similar toa subscribing to an electric utility to access electrical energy, atelephone utility to access telephonic services, etc.

For purposes of brevity, only a memory storage device 1146 isillustrated with remote computer(s) 1144. Remote computer(s) 1144 islogically connected to computer 1112 through a network interface 1138and then physically connected by way of communication connection 1150.Network interface 1148 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies comprise fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies comprise, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1150 refer(s) to hardware/software employedto connect network interface 1148 to bus 1118. While communicationconnection 1150 is shown for illustrative clarity inside computer 1112,it can also be external to computer 1112. The hardware/software forconnection to network interface 1148 can comprise, for example, internaland external technologies such as modems, comprising regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, comprising what is described in the Abstract, is notintended to be exhaustive or to limit the disclosed embodiments to theprecise forms disclosed. While specific embodiments and examples aredescribed herein for illustrative purposes, various modifications arepossible that are considered within the scope of such embodiments andexamples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can comprise packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks comprisebroadcast technologies (e.g., sub-Hertz, extremely low frequency, verylow frequency, low frequency, medium frequency, high frequency, veryhigh frequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc.; femtocell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

The term “infer” or “inference” can generally refer to the process ofreasoning about, or inferring states of, the system, environment, user,and/or intent from a set of observations as captured via events and/ordata. Captured data and events can include user data, device data,environment data, data from sensors, sensor data, application data,implicit data, explicit data, etc. Inference, for example, can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events. Inference can also refer to techniquesemployed for composing higher-level events from a set of events and/ordata. Such inference results in the construction of new events oractions from a set of observed events and/or stored event data, whetherthe events, in some instances, can be correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources. Various classification schemes and/or systems(e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, and data fusion engines) can beemployed in connection with performing automatic and/or inferred actionin connection with the disclosed subject matter.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A first device, comprising: a processor; and amemory that stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: determiningan aggregation level for application by a second device to decodecandidate downlink control channels associated with a control channelresource set; and sending aggregation level information to the seconddevice indicating the aggregation level.
 2. The first device of claim 1,wherein, based on the sending, the second device is configured to applythe aggregation level in association with attempting to decode thecandidate control downlink control channels.
 3. The first device ofclaim 1, wherein the determining the aggregation level comprisesselecting the aggregation level from a group of candidate aggregationlevels based on a defined criterion.
 4. The first device of claim 1,wherein the determining the aggregation level comprises determining theaggregation level based on capability information indicating aggregationlevels supported by the second device.
 5. The first device of claim 1,wherein the determining the aggregation level comprises determining theaggregation level based on a location of the second device.
 6. The firstdevice of claim 1, wherein the determining the aggregation levelcomprises determining the aggregation level based on a distance betweenthe second device and the first device.
 7. The first device of claim 6,wherein the determining the aggregation level comprises selecting afirst aggregation level based on the distance being less than a defineddistance and selecting a second aggregation level based on the distancebeing greater than the defined distance, and wherein the firstaggregation level is lower than the second aggregation level.
 8. Thefirst device of claim 1, wherein the determining the aggregation levelcomprises determining the aggregation level based on a geometryassociated with the second device.
 9. The first device of claim 8,wherein the determining the aggregation level comprises selecting afirst aggregation level based on the geometry being less than a definedvalue and selecting a second aggregation level based on the geometrybeing greater than the defined value, and wherein the first aggregationlevel is higher than the second aggregation level.
 10. The first deviceof claim 1, wherein the determining the aggregation level comprisesselecting the aggregation level from a group of candidate aggregationlevels based on a combination of criteria selected from a group ofcriteria consisting of: a first criterion applicable to an aggregationlevel capability of the second device, a second criterion applicable toa location of the second device relative to the first device, and athird criterion applicable to a geometry associated with the seconddevice.
 11. The first device of claim 1, wherein the sending theaggregation level information comprises employing a signaling protocolclassified as a higher layer signaling protocol.
 12. The first device ofclaim 11, wherein the signaling protocol comprises a radio resourcecontrol signaling protocol or a media access control protocol.
 13. Amethod, comprising: determining, by a first device operatively coupledto a processor, an aggregation level for application by a second deviceto decode candidate downlink control channels associated with a controlchannel resource set; and transmitting, by the first device, aggregationlevel information to the second device indicating the aggregation level.14. The method of claim 13, wherein, as a result of the transmitting,the second device is enabled to apply the aggregation level inassociation with attempting to decode the candidate control downlinkcontrol channels.
 15. The method of claim 13, wherein the determiningthe aggregation level comprises selecting the aggregation level from agroup of candidate aggregation levels based on a defined criterion. 16.The method of claim 15, wherein the defined criterion is selected from agroup of criteria consisting of: a first criterion applicable to anaggregation level capability of the second device, a second criterionapplicable to a location of the second device relative to the firstdevice, and a third criterion applicable to a geometry associated withthe second device.
 17. The method of claim 13, wherein the transmittingthe aggregation level information comprises employing a signalingprotocol classified as a higher layer signaling protocol.
 18. A firstdevice, comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: receiving aggregation levelinformation from a second device indicating an aggregation level for acontrol channel resource set, wherein the aggregation level was selectedby the second device from candidate aggregation levels based on adefined criterion; and based on the receiving, employing the aggregationlevel in association with attempting to decode candidate downlinkcontrol channels associated with the control channel resource set. 19.The first device of claim 18, wherein the defined criterion is evaluatedwith respect to a group of device criteria consisting of: an aggregationlevel capability of the first device, a location of the first devicerelative to the second device, and a geometry associated with the firstdevice.
 20. The first device of claim 18, wherein the aggregation levelinformation comprises first aggregation level information, wherein theaggregation level comprises a first aggregation level, and wherein theoperations further comprise: receiving second aggregation levelinformation from the second device indicating a second aggregation levelfor the control channel resource set, wherein the second aggregationlevel was selected by the second device from the candidate aggregationlevels based on a change to the defined criterion; and based on thereceiving, employing the second aggregation level instead of the firstaggregation level in association with the attempting to decode thecandidate downlink control channels.